Enhanced network performance monitoring

ABSTRACT

There are disclosed measures for enhancing network performance monitoring. Such measures may for example comprise receiving a report on measurements of terminal-related network performance parameters from a terminal, acquiring information of access network-related network performance parameters, and combining the received terminal-related network performance parameters and the acquired access network-related network performance parameters into a combined network performance report.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.13/504,171, which is the National Stage of International Application No.PCT/EP2009/064294, filed Oct. 29, 2009.

TECHNICAL FIELD

The present invention generally relates to techniques for enhancednetwork performance monitoring. Stated in other words, the presentinvention relates to enhancements in collecting and/or reportingperformance data such as for example network performance data beingusable for network coverage and/or capacity optimization purposes.

BACKGROUND

Network performance monitoring, i.e. collecting and/or reporting networkperformance data, is a vital task for network operators of any kind ofcommunication network. A clear and complete picture of networkperformance, in particular in geographical problem areas or geographicalareas intended for deployment of new network facilities, is importantfor the operator in order to be able to appropriately plan, deploy, andcontrol its network facilities, or to enable self-optimization ofnetworks.

In an effort to gain such a clear and complete picture of networkperformance, drive tests are usually employed, in which networkperformance data are gathered by cruising around, e.g. by car or train,and performing measurements of network performance parameters by meansof a terminal device, e.g. a user equipment UE. Thereby,terminal-related network performance parameters may be measured eithermanually or automatically.

While manual and extensive drive tests have previously been common andnecessary, automation as well as minimization of drive tests iscurrently desired to reduce network operation and maintenance costs,ensure faster optimization cycles, and to protect the environment byreducing carbon emissions.

In the following, reference is made to current efforts in automating andminimizing drive tests, which is intended as a non-limiting example forimpacts of network performance monitoring.

Minimizing drive tests has currently been addressed in 3GPP (ThirdGeneration Partnership Program), with the scope of the work beingfeasibility, benefits and complexity of automating the collection of UEmeasurements to minimize the need of manual drive tests. In this regard,the necessity of defining new capabilities for logging and reporting UEmeasurements for minimizing drive tests is being investigated.

A recent study on minimization of drive tests in next generationnetworks covers use cases defined in this field and some UE measurementsaddressing these use cases. The identified use cases aim to enableautomatic methods for monitoring of network parameters.

In order to replace drive tests performed manually, new UE measurementlogs (i.e. sets of measurements of specific entities) have beenproposed. Corresponding UE measurements should be taken at theoccurrence of a predefined trigger, which can be either periodical or aspecific event, e.g. a failure event. In addition, location informationcould be attached to the measurements, if available, to makegeographical areas distinguishable, which differ in network quality. TheUE reports information based on the log it has provided.

However, when only the UE is sending measurement reports, as currentlyproposed, an analysis of the report, which is delivered periodically orwhen the terminal has encountered a problem, can not be sufficientlyaccurate. This is due to the lack of any information about theunderlying network situation or network-related aspects of networkperformance, i.e. current and previous network performance data from theperspective of the network such as e.g. the (radio) access network.Since such information on the underlying network situation is expedientfor a proper analysis of the overall network performance, the findingson the basis of an (incomplete) measurement report from the terminal aredevaluated because of being weighted down with lost knowledge of thenetwork performance.

Accordingly, in view of the above, there is a need for techniques forenabling the finding of a clear and complete picture of networkperformance even in automated and/or minimized network performancemonitoring.

SUMMARY OF EXEMPLARY EMBODIMENTS OF THE INVENTION

Embodiments of the present invention are made to provide for a feasiblesolution for enhanced network performance monitoring. In particular, butnot exclusively, embodiments of the present invention are made toovercome or at least mitigate above-outlined problems and drawbacks.

According to an exemplary first aspect of the present invention, thereis provided a method comprising receiving a report on measurements ofterminal-related network performance parameters from a terminal,acquiring information of access network-related network performanceparameters, and combining the received terminal-related networkperformance parameters and the acquired access network-related networkperformance parameters into a combined network performance report.

According to further developments and/or modifications thereof, one ormore of the following applies:

-   -   the acquiring further comprises determining a triggering event        and/or use case of the received measurement report on the basis        of a predefined association between a triggering event and/or        use case and measurements to be performed at the terminal, and        selecting access network-related network performance parameters        to be acquired based on the determined triggering event and/or        use case,    -   the method further comprises forwarding the combined network        performance report to a network management element and/or an        operation and maintenance element for network performance        analysis and/or control,    -   the method is operable at a device management element being        interconnected with an access network element,    -   the measurement report is received as user plane data from the        terminal,    -   the access network-related network performance parameters are        acquired externally from the access network element,    -   the method is operable at an access network element,    -   the measurement report is received as control plane data from        the terminal,    -   the access network-related network performance parameters are        acquired internally at the access network element,    -   the device management element comprises an open mobile alliance        device management server, and/or    -   the access network element comprises one of a base station, a        base transceiver station, a NodeB, and an eNodeB.

According to an exemplary second aspect of the present invention, thereis provided an apparatus comprising a receiver configured to receive areport on measurements of terminal-related network performanceparameters from a terminal, and an acquisition unit configured toacquire information of access network-related network performanceparameters, and a combination unit configured to combine the receivedterminal-related network performance parameters and the acquired accessnetwork-related network performance parameters into a combined networkperformance report.

According to further developments and/or modifications thereof, one ormore of the following applies:

-   -   the apparatus further comprises a determination unit configured        to determine a triggering event and/or use case of the received        measurement report on the basis of a predefined association        between a triggering event and/or use case and measurements to        be performed at the terminal, and a selection unit configured to        select access network-related network performance parameters to        be acquired based on the determined triggering event and/or use        case,    -   the apparatus further comprises a transmitter configured to        forward the combined network performance report to a network        management element and/or an operation and maintenance element        for network performance analysis and/or control,    -   the apparatus is operable as or at a device management element        being interconnected with an access network element,    -   the receiver is configured to receive the measurement report as        user plane data from the terminal,    -   the acquisition unit is configured to acquire the access        network-related network performance parameters externally from        the access network element,    -   the apparatus is operable as or at an access network element,    -   the receiver is configured to receive the measurement report as        control plane data from the terminal,    -   the acquisition unit is configured to acquire the access        network-related network performance parameters internally at the        access network element,    -   the device management element comprises an open mobile alliance        device management server, and/or    -   the access network element comprises one of a base station, a        base transceiver station, a NodeB, and an eNodeB.

According to an exemplary third aspect of the present invention, thereis provided a computer program product comprising program code meansbeing arranged, when run on a processor of an apparatus, to perform themethod according to the above first aspect or any one of the furtherdevelopments and/or modifications thereof. The apparatus, on which saidcomputer program product may be run, is the apparatus according to theabove second aspect or any one of the further developments and/ormodifications thereof.

According to any one of the above aspects or any one of the furtherdevelopments and/or modifications thereof, one or more of the followingapplies:

-   -   the terminal-related and/or the access network-related network        performance parameters comprise parameters specific to one of        minimization of drive tests for network performance monitoring        and self optimization of networks,    -   the terminal-related and/or the access network-related network        performance parameters are associated with at least one of use        cases for coverage optimization, mobility optimization, capacity        optimization, parameterization for common channels,        quality-of-service verification    -   the measurements of terminal-related network performance        parameters comprise one or more of periodical radio environment        or downlink pilot measurements, radio environment measurements        when a serving cell becomes worse than a threshold, transmit        power headroom and radio environment measurements when a        terminal's transmit power becomes less than a threshold, random        access details and radio environment measurements when a random        access failure occurs, radio environment, location, time and        cell identity measurements when a paging channel failure occurs,        and radio environment, location, time, cell identity and        frequency measurements when a broadcast channel failure occurs,        and/or    -   the information on access network-related network performance        parameters relates to one or more of access restriction        parameters, network load parameters, traffic distribution        parameters, congestion parameters, radio and/or hardware        resource parameters, handover parameters, mobility parameters,        dynamic connection parameters, signaling error parameters, and        signaling events on a X2 interface between access network        elements.

By way of exemplary embodiments of the present invention, there areprovided techniques for enhanced network performance monitoring, forexample for enhancements in collecting and/or reporting performance datasuch as network performance data.

By way of exemplary embodiments of the present invention, there areprovided techniques for an involvement of an access network element suchas e.g. an eNodeB in network performance monitoring and/or controlling.The involvement of the access network element is capable ofadvantageously complementing (network) performance monitoring and/orcontrolling enabled by a terminal.

By way of exemplary embodiments of the present invention, networkperformance monitoring and/or controlling may be accomplished by both aterminal conditions, such as terminal-related (network performance)parameters, and network conditions, such as access network-relatednetwork performance parameters.

By way of exemplary embodiments of the present invention, drive testsfor network performance monitoring may be minimized and automated, whilestill enabling the finding of a clear and complete picture of networkperformance, and/or self-optimization of networks may be facilitated.

Further details may become more apparent from the subsequent descriptionof exemplary embodiments with reference to accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

In the following, exemplary embodiments of the present invention will bedescribed in greater detail by way of non-limiting examples withreference to the accompanying drawings, in which

FIG. 1 shows a flowchart of a method according to exemplary embodimentsof the present invention,

FIG. 2 shows a schematic overview of a first system architectureaccording to exemplary embodiments of the present invention,

FIG. 3 shows details of a structure and procedures of the first systemarchitecture according to exemplary embodiments of the presentinvention,

FIG. 4 shows a schematic overview of a second system architectureaccording to exemplary embodiments of the present invention,

FIG. 5 shows details of a structure and procedures of the second systemarchitecture according to exemplary embodiments of the presentinvention,

FIG. 6 shows a flowchart of a method according to exemplary embodimentsof the present invention,

FIG. 7 shows a block diagram of an apparatus according to exemplaryembodiments of the present invention, and

FIG. 8 shows a block diagram of an apparatus according to exemplaryembodiments of the present invention.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS OF THE INVENTION

The present invention is described herein with reference to particularnon-limiting examples. A skilled person will appreciate that theinvention is not limited to these examples, and may be more broadlyapplied.

In particular, the present invention and its embodiments are mainlydescribed in relation to 3GPP specifications being used as non-limitingexamples for certain exemplary network configurations and deployments.In particular, minimization of drive test for network performancemonitoring on the basis of a 3GPP-based network is used as anon-limiting example for the applicability of thus described exemplaryembodiments. As such, the description of exemplary embodiments givenherein specifically refers to terminology which is directly relatedthereto. Such terminology is only used in the context of the presentednon-limiting examples, and does naturally not limit the invention in anyway. Rather, any other network configuration or system deployment, etc.may also be utilized as long as compliant with the features describedherein.

In particular, embodiments of the present invention may be applicable inany system with the need for monitoring network performance preferablywith minimum efforts in an automated manner, such as for example inself-optimizing networks, irrespective of the underlying networkenvironment. Embodiments of the present invention may be applicablefor/in any kind of modern and future communication network includingmobile/wireless communication networks, such as for example GlobalSystem for Mobile Communication (GSM), General Packet Radio Service(GPRS), Universal Mobile Telecommunication System (UMTS), Wideband CodeDivision Multiple Access (WCDMA), Long-Term Evolution (LTE), Long-TermEvolution Advanced (LTE-A), Wireless Interoperability for MicrowaveAccess (WiMAX), evolved High Rate Packet Data (eHRPD), Evolved PacketCore (EPC), or other 3GPP (3GPP: Third Generation Partnership Project)or IETF (Internet Engineering Task Force) networks.

Hereinafter, various embodiments and implementations of the presentinvention and its aspects or embodiments are described using severalalternatives. It is generally to be noted that, according to certainneeds and constraints, all of the described alternatives may be providedalone or in any conceivable combination (also including combinations ofindividual features of the various alternatives).

In the following, exemplary embodiments of the present invention aredescribed with reference to methods, procedures and functions.

FIG. 1 shows a flowchart of a method according to exemplary embodimentsof the present invention. The thus depicted method may for example beexecuted at device management element such as a device management serverexemplarily being compliant with OMA (Open Mobile Alliance)specifications, as exemplified in the system architecture of FIGS. 3 and4 below, or at an access network element such as a base (transceiver)station, NodeB or eNodeB, as exemplified in the system architecture ofFIGS. 5 and 6 below.

According to the exemplary method of FIG. 1, in operation S110, theexecuting apparatus (e.g. a receiver thereof) receives a report onmeasurements of terminal-related network performance parameters from aterminal such as a user equipment UE, i.e. a UE measurement log. Suchterminal-related network performance parameters may be measured andreported in accordance with one or more predefined triggers which may beperiodical or based on the occurrence of a failure event. Specific setsof such terminal-related network performance parameters may bepredefined for measurement and reporting purposes depending on atriggering event and/or use case thereof. For example, one or morespecific set of relevant network performance parameters, i.e. one ormore specific UE measurement logs, may—in terms of minimizing drivetests—be associated with any one of use cases for coverage optimization,mobility optimization, capacity optimization, parameterization forcommon channels, quality-of-service verification. For example, such UEmeasurement logs may comprise one or more of periodical radioenvironment or downlink pilot measurements, radio environmentmeasurements when a serving cell becomes worse than a threshold,transmit power headroom and radio environment measurements when aterminal's transmit power becomes less than a threshold, random accessdetails and radio environment measurements when a random access failureoccurs, radio environment, location, time and cell identity measurementswhen a paging channel failure occurs, and radio environment, location,time, cell identity and frequency measurements when a broadcast channelfailure occurs. Radio resource measurements in this regard may relate toCPICH (common pilot channel), RSCP (received signal code power), RSRP(reference signal received power), and/or RSRQ (reference signalreceived quality). A paging channel failure may relate to decoding errorof the PDCCH (physical downlink control channel).

The above-described receiving may, depending on an underlying systemscenario, be accomplished by way of a user plane transport (as in thecase of FIGS. 3 and 4) or a control plane transport (as in the case ofFIGS. 5 and 6).

In operation S120, the executing apparatus (e.g. a processor ordedicated acquisition unit thereof) acquires information of accessnetwork-related network performance parameters, e.g. (e)NodeB or basestation information. On the one hand, all available accessnetwork-related network performance parameters may be acquired uponreceipt of a UE measurement log in operation S110 (in which case thesubsequently described determination and selection operations aredispensable). On the other hand, such access network-related networkperformance parameters may be associated with one or more predefinedtrigger events and/or use cases for logging and/or reporting networkperformance parameters at the terminal. Accordingly, on the basis of the(set of) measurements of terminal-related network performance parametersreceived in operation S110 and a predefined association, a triggeringevent and/or use case of the received measurement report may bedetermined (S121), and (a specific set of) access network-relatednetwork performance parameters to be acquired may be selected out of allavailable parameters (S122). For example, one or more specific set ofrelevant network performance parameters, e.g. one or more specific(e)NodeB or base station information sets, may—in terms of minimizingdrive tests—be associated with any one of use cases for coverageoptimization, mobility optimization, capacity optimization,parameterization for common channels, quality-of-service verification.For example, the information on access network-related networkperformance parameters may relate to one or more of access restrictionparameters, network load parameters (e.g. concerning an own cell or oneor more neighboring cells of the (e)NodeB or base station), trafficdistribution parameters, congestion parameters, radio and/or hardwareresource parameters, handover parameters (e.g. information on possibleinitiated or failed handover attempts; information if the (e)NodeB orbase station in question or a potential handover candidate hasexperienced e.g. an overload problem or has been reset e.g. due to asoftware problem), mobility parameters (e.g. mobility historyinformation concerning e.g. an identity of a previous cell of aterminal), dynamic connection parameters (e.g. information on possibledynamic parameters which may impact a connection, such as power forreference symbols, or possible activation/deactivation of carriers onsome frequency or frequencies (e.g. in the context of LTE-A carrieraggregation)), signaling error parameters (e.g. possible error cases forsignaling connections such as RRC (radio resource control) connections),signaling events on a X2 interface between access network elements, aswell as other information from a device like the terminal (e.g. reportedpower headroom or reported latest CQI/CSI (CAI: channel qualityindicator, CSI: channel state information) messages). For instance, amobility optimization use case depends upon mobility and handoverparameters.

The above-described acquisition may, depending on an underlying systemscenario, be accomplished internally at the executing apparatus (as inthe case of FIGS. 5 and 6) or externally from an external apparatusbeing interconnected with the executing apparatus (as in the case ofFIGS. 3 and 4).

In operation S130, the executing apparatus (e.g. a processor ordedicated combination unit thereof) combines the receivedterminal-related network performance parameters and the acquired accessnetwork-related network performance parameters, which may be allavailable parameters or a set of parameters being determined out of allavailable parameters) into a combined network performance report. Such acombining may, depending on an underlying system scenario, beaccomplished by way of an attachment of the e.g. eNodeB information tothe received UE measurement report (as in the case of FIGS. 3 and 4),when the combining takes place at an executing apparatus other than theUE and the e.g. eNodeB, or by way of a complementation of the receivedUE measurements by e.g. the eNodeB information (as in the case of FIGS.5 and 6), when the combining takes place at the e.g. eNodeB where therelevant access network-related parameters are available anyhow.

In operation S140, the executing apparatus (e.g. a transmitter) mayforward the thus created combined network performance report for networkperformance analysis and/or control. Yet, the forwarding may also beomitted in case network performance analysis and/or control on the basisof the thus gathered and combined parameters may be accomplished at theexecuting apparatus. The forwarding may, depending on an underlyingsystem scenario, be accomplished towards a network management elementsuch as a NM/IRP manager (NM: network management, IRP: integratedreference point) (as in the case of FIGS. 3 and 4) or towards an O&M(operation and maintenance) element (as in the case of FIGS. 5 and 6).

The above-described procedure may be equally applicable for minimizingdrive tests (MDT) and/or for self-optimizing network (SON). Then, theterminal-related and/or the access network-related network performanceparameters comprise parameters specific to MDT and/or SON.

In the following, two examples of system architectures for implementingexemplary embodiments of the present invention are described.

As a first exemplary system scenario, a user plane (UP) basedarchitecture is explained.

FIG. 2 shows a schematic overview of a first system architecture, i.e. aUP-based system architecture, according to exemplary embodiments of thepresent invention.

According to the exemplary architecture of FIG. 2, a user equipment UErepresenting a terminal logs measurements of terminal-related networkperformance parameters as described above, and reports the same to a DMSrepresenting a device management element, wherein such a reporting takesplace on the user plane and is transparent to a radio access network,i.e. to an eNode representing an access network element. The eNodeB,e.g. upon request from the DMS, gathers information of accessnetwork-related network performance parameters as described above, andreports the same to the DMS. Since the eNodeB is, for example, aware ofX2 signaling events on an interface towards another eNodeB, such X2signaling events may be included in the thus reported eNodeBinformation. At the DMS, the reports from the UE and the eNodeB arecombined, e.g. by attaching the eNodeB information to the UE measurementreport. The thus created combined report may be forwarded to a NM/IRPmanager representing a network management and/or operation andmaintenance element.

FIG. 3 shows details of a structure and procedures of the first systemarchitecture, as outlined in FIG. 2, according to exemplary embodimentsof the present invention.

According to the exemplary structure of FIG. 3, the user equipment UEmay also comprise or operate as a device management (DM) clientcooperating with the DMS at which the above-described procedure of FIG.1 is executed. The DMS may comprise a DM server unit and an IRP agentunit cooperating with an IRP manager or an IRP manager unit at a networkmanagement element or the like. A transport between UE and DMS, which iseffected on the user plane in a manner transparent to a radio accessnetwork, may be accomplished by means of a OMA DM protocol.

According to the exemplary procedures of FIG. 3, the UE, in particularits configurations for measuring and reporting terminal-related networkperformance parameters as described above, may be configured by the DMS.For example, a configuration for measurement logs, e.g. which (set of)parameters are to be measured for which use case or the like, and aconfiguration for reporting triggers, e.g. which triggers and which kindof triggers (e.g. periodical or failure-based) are effective for whichmeasurements and/or use cases, are sent from the DMS to the UE prior toany actual network performance operation. A configuration formeasurement logs may comprise e.g. instructions as to whatentities/parameters are to be measured, when a failure event is met,such as when a cell becomes worse than a threshold. A configuration forreporting triggers may comprise e.g. instructions as to whether a reportis to be sent immediately upon measurement, on network demand, or in aperiodical manner such as every 24 hours at 3 a.m.

When a thus configured measurement trigger is met, the UE takes acorresponding measurement log. When a thus configured reporting triggeris met, the UE reports the thus taken measurement log (report) to theDMS. Upon receipt thereof, the DMS acquires corresponding accessnetwork-related network performance parameters, which in the presentexample case takes place by requesting such relevant information from aneNodeB representing an access network element of the access network inquestion, where such information are available or will be gathered uponrequest. The DMS may also determine and select a specific (sub-)set ofaccess network-related parameters based on a reporting trigger and/oruse case pertaining to the measurements received from the UR. The thusacquired, i.e. received, parameters are then combined with those beingreceived from the UE into a combined network performance report. Thiscombined report including UE data (relating to a terminal situation) andeNodeB information (relating to a (access) network situation) may thenbe forwarded to an NM/IRP manager via an integrated reference point(IRP), which has requested these network parameters, e.g. for networkperformance monitoring and/or control.

For the purpose of exchanging information between DMS and eNodeB, thereis assumed the existence of a corresponding interface or referencepoint, such as e.g. an OMA DM interface. In addition, there is assumed amanner of requesting and transporting eNodeB complement information,which may be any conceivable manner.

As indicated above, the measurements, the measurement report, and thecombined report may be specific to MDT and/or SON, respectively.

As a second exemplary system scenario, a control plane (CP) basedarchitecture is explained.

FIG. 4 shows a schematic overview of a second system architecture, i.e.a CP-based system architecture, according to exemplary embodiments ofthe present invention.

According to the exemplary architecture of FIG. 4, a user equipment UErepresenting a terminal logs measurements of terminal-related networkperformance parameters as described above, and reports the same to aeNodeB representing an access network element, wherein such a reportingtakes place on the control plane. The eNodeB then gathers information ofaccess network-related network performance parameters as describedabove. Since the eNodeB is, for example, aware of X2 signaling events onan interface towards another eNodeB, such X2 signaling events may beincluded in the thus gathered eNodeB information. Then, the eNodeBcombines the parameters received from the UE and the parameters gatheredlocally at the eNodeB, e.g. by attaching the eNodeB information to theUE measurement report. The thus created combined report may be forwardedto a O&M device representing a network management and/or operation andmaintenance element.

FIG. 5 shows details of a structure and procedures of the second systemarchitecture, as outlined in FIG. 4, according to exemplary embodimentsof the present invention.

According to the exemplary structure of FIG. 5, the user equipment UE isconnected with an eNodeB, which is connected to an O&M device, and whichmay also be connected to one or more other eNodeB's via a X2 interface,respectively. The above-described procedure of FIG. 1 is executed at theeNodeB cooperating with the UE. A transport between UE and relevanteNode is effected on the control plane.

According to the exemplary procedures of FIG. 5, the UE, in particularits configurations for measuring and reporting terminal-related networkperformance parameters as described above, may be configured by theeNodeB. In this regard, the same notions as outlined above in connectionwith FIG. 3 apply here accordingly.

When a thus configured measurement trigger is met, the UE takes acorresponding measurement log. When a thus configured reporting triggeris met, the UE reports the thus taken measurement log (report) to theeNodeB. Upon receipt thereof, the eNodeB acquires corresponding accessnetwork-related network performance parameters, which in the presentexample case takes place internally at the eNodeB, e.g. by querying therequired information from a storage and/or performing correspondingmeasurements. The eNodeB may also determine and select a specific(sub-)set of access network-related parameters based on a reportingtrigger and/or use case pertaining to the measurements received from theUE. The thus acquired, i.e. received, parameters are then combined withthose being received from the UE into a combined network performancereport. This combined report including UE data (relating to a terminalsituation) and eNodeB information (relating to a (access) networksituation) may then be forwarded to an O&M device via an Interface-N(Itf-N) which is built up by a number of IRPs (integrated referencepoints) and a related name conversion. The O&M device may havepreviously these network parameters, e.g. for network performancemonitoring and/or control.

As indicated above, the measurements, the measurement report, and thecombined report may be specific to MDT and/or SON, respectively.

Hereinbefore, it is always assumed that a connection between theterminal and the network persists during network performance monitoringand/or control. However, there may also occur a situation in which theconnection between terminal and network is disconnected before theabove-described operations are completed. Thus, the reporting ofterminal-related network performance parameters to the DMS or the eNodeBmay be disabled or delayed, thus affecting the further operations ofnetwork performance monitoring and/or control.

For example, a terminal connection may be lost due to a sudden effectsuch as the driving into tunnel without radio access coverage. If so,the terminal may not be able to send its measurement report, and/or thenetwork side may not be able to initiate any specific problem report forhandling such a situation before the connection is lost.

In the exemplary situation of a CP-based architecture according to FIGS.4 and 5, it may for example be the case that the UE, after having beendisconnected from the eNodeB, re-enters network coverage in the area ofanother eNodeB. Such a case is quite likely in case of a tunnel beingpassed by the UE. Then, the previous eNodeB will vainly wait for thereceipt of UE measurements, which would disable the further operationsas described above.

Accordingly, operations are needed for dealing with the case that UEmeasurement may not be received where they are needed for networkperformance monitoring and/or control purposes.

FIG. 6 shows a flowchart of a method according to exemplary embodimentsof the present invention.

In operation S610, a necessity of reporting access-related networkperformance parameters may be detected, for example by expiry of a timersince the previous report of such parameters or since receipt of an UEmeasurement report, detection of connection loss towards the UE, or thelike. Then, in operation S620, access-related network performanceparameters may be (internally or externally) acquired as describedbeforehand. Then, if current terminal-related network performanceparameters are available (i.e. YES in S630), a combined report may becreated (and forwarded) anyhow in operation S640. Yet, if no currentterminal-related network performance parameters are available (i.e. NOin S630), there may be created a report in operation S650, whichcontains access network-related network performance parameters but noterminal-related network performance parameters are available. In orderto enable the later on supplementing with such terminal-related networkperformance parameters (at the present or any other entity), this reportmay contain a placeholder for such parameters and/or informationenabling the later combination with such parameters.

In this regard, a non-combined report according to operation S650 may besent with a time stamp being included therein. This may facilitateobservance of temporal relations in the further operations. Although notillustrated in FIG. 6, the terminal, after having been re-connected withthe new eNodeB, may provide an error report or a log of thedisconnecting event having been occurred in addition to its measurementreport. This may facilitate the further operation by providing knowledgeabout the cause of the disconnection, which may also contribute tonetwork performance monitoring and/or control.

Thereby, a report of access network-related network performanceparameters is possible when required even if no terminal-related networkperformance parameters are available, i.e. without the need to wait forthe receipt of UE measurements which could never arrive due to aprevious inter-eNodeB handover.

An operation as exemplarily illustrated by FIG. 6 may for example beexecuted at a DMS entity according to FIGS. 2 and 3, an O&M entityaccording to FIGS. 4 and 5, and/or an eNodeB according to any one ofFIGS. 2 to 5.

In case of an execution at an eNodeB according to any one of FIGS. 2 to5, the operations S630 and S640 may be omitted, and the report with theaccess network-related network performance parameters may be forwardedtowards the DMS.

In case of an execution at DMS/O&M according to any one of FIGS. 2 to 5,even if operation S650 is performed first, operation S640 may then beperformed after intermediate receipt of necessary terminal-relatednetwork performance parameters.

It is to be noted that the operations of FIGS. 1 and 6 may be performedindependent of each other as well as in any conceivable combination interms of a co-located execution at a single entity or a distributionover different entities and in terms of a temporal flow. Stated in otherwords, effects of exemplary embodiments of the present inventiondescribed herein may be outlined as follows.

The enhanced reporting data containing UE measurement logs (e.g. definedfor MDT purposes) accompanied by network information enables a moreefficient diagnosis of a certain problem or failure situation in thenetwork. As describe above, the monitoring of predefined triggers isperformed at the UE side. When a specific event happens, the UE performsrelevant measurements depending on the triggering event, which isassociated further with one or more specific use case(s). Each event andnetwork problem is associated with a relevant set of parameters at thenetwork side. For instance, a mobility optimization use case dependsupon mobility and handover parameters, which reside at the network.Therefore, the number of network information, by which the UEmeasurements are complemented according embodiments of the presentinvention, has a value when determining the reason or evaluation ofproblems experienced by an end-user. Accordingly, measurements comingfrom the UE are jointly taken into account with appropriate networkdata.

In principle, an implementation of embodiments of the present inventionis independent of architectural aspects, i.e. a transport mechanismutilized for UE measurement reporting. According to the above examplesof system architectures, the network entity (OMA DM server or eNodeB)responsible for policy control and/or configuration of measurementslogging may assist the reports from the UE and the network information.In case of a user plane based architecture, DMS is the recipient of thereports sent from the UE and the eNodeB. Therefore, as an independentnetwork entity, the DMS is able to communicate with an eNodeB and torequest relevant network information available to serve, since beingnormally operated at the eNodeB. In case of a control plane basedarchitecture, eNodeB is the recipient of the reports sent from the UEand the point where eNodeB information is available. This approach issimpler and easier in terms of data reporting from the network side,since the network entity is basically the eNodeB itself. Besides, theradio interface utilized to configure and report UE measurements isprepared and available for service.

Anyhow, regardless of the transport mechanism utilized, the merit ofembodiments of the present invention is that problems or deficiencies innetwork performance monitoring and/or controlling (e.g. for MDTpurposes) may be efficiently overcome. While different measurementsprovided by the UE are complemented by respective eNodeB information,detection probability for network problems and/or failures increases.For example, the UE and eNodeB feedback help to ease the operator burdento perform live drive testing and result in OPEX (operatingexpenditures) savings. In addition, it is advantageous that the reportsfrom the UE may be categorized depending on the network situation when acertain event occurred, and thus a required analysis is easier forsolving the network problems and/or failures. Many of the requirednetwork-related information is readily available at the eNodeB. The UEmeasurements considered separately may then, for example, be used alsofor e.g. SON purposes. That also allows utilizing the same UEfunctionality for different functions (e.g. MDT and SON) with avoidanceof redundant implementation complexity.

While in the foregoing exemplary embodiments of the present inventionare described mainly with reference to methods, procedures andfunctions, corresponding exemplary embodiments of the present inventionalso cover respective apparatuses, network nodes and systems, includingboth software and/or hardware thereof.

Respective exemplary embodiments of the present invention are describedbelow referring to FIGS. 7 and 8, while for the sake of brevityreference is made to the detailed description of respectivecorresponding methods and operations according to FIGS. 1 to 6,respectively.

In FIGS. 7 and 8 below, the solid line blocks are basically configuredto perform respective operations as described above. The entirety ofsolid line blocks are basically configured to perform the methods andoperations as described above, respectively. With respect to FIGS. 7 and8, it is to be noted that the individual blocks are meant to illustraterespective functional blocks implementing a respective function, processor procedure, respectively. Such functional blocks areimplementation-independent, i.e. may be implemented by means of any kindof hardware or software, respectively. The arrows interconnectingindividual blocks are meant to illustrate an operational couplingthere-between, which may be a physical and/or logical coupling, which onthe one hand is implementation-independent (e.g. wired or wireless) andon the other hand may also comprise an arbitrary number of intermediaryfunctional entities not shown. The direction of arrow is meant toillustrate the direction in which certain operations are performedand/or the direction in which certain data is transferred.

Further, in FIGS. 7 and 8, only those functional blocks are illustrated,which relate to any one of the above-described methods, procedures andfunctions. A skilled person will acknowledge the presence of any otherconventional functional blocks required for an operation of respectivestructural arrangements, such as e.g. a power supply, a centralprocessing unit, respective memories or the like. Among others, memoriesare provided for storing programs or program instructions forcontrolling the individual functional entities to operate as describedherein.

FIG. 7 shows a block diagram of an apparatus according to exemplaryembodiments of the present invention. In view of the above, the thusdescribed apparatus may be implemented by or at a device managementelement such as e.g. a DMS according to FIGS. 2 and 3, or an accessnetwork element such as e.g. an eNodeB according to FIGS. 4 and 5.

According to FIG. 7, the apparatus according to exemplary embodiments ofthe present invention is configured to perform a method as described inconjunction with FIG. 1. Therefore, while basic operations are describedhereinafter, reference is made to the above description for details.

According to an exemplary embodiment depicted in FIG. 7, the thusdepicted apparatus comprises a receiver, an acquisition unit, acombination unit, a determination unit, a selection unit, and atransmitter. It is to be noted that the one or more of the acquisition,combination, determination, and selection units may be implemented by aprocessor. Further, it is to be noted that the determination andselection units may be omitted in case no selection of appropriatenetwork performance parameters is desired. For a basic implementation,the transmitter may also be omitted, as the forwarding of a combinedreport is not necessary according to all embodiments of the presentinvention.

The receiver may be configured to receive a report on measurements ofterminal-related network performance parameters from a terminal, thusrepresenting means for receiving such terminal information. The receivermay be configured to receive the measurement report from the terminal asuser plane data or as control plane data. The acquisition unit may beconfigured to acquire information of access network-related networkperformance parameters, thus representing means for acquiring suchnetwork information. As outlined above, the acquisition unit may beconfigured to accomplish the acquisition externally, e.g. from an accessnetwork element, or internally, e.g. at an access network element. Theexternal acquisition may be applicable when the thus depicted apparatuslocated at a DMS or the like, and may be accomplished by way of aninterface (transceiver) towards an eNodeB or the like. The internalacquisition may be applicable when the thus depicted apparatus locatedat an eNodeB or the like, and may be accomplished by way of a localstorage and/or a measuring unit. The combination unit is configured tocombine the received terminal-related network performance parametersfrom the receiver and the acquired access network-related networkperformance parameters from the acquisition unit, e.g. into a combinednetwork performance report, thus representing means for combiningrelevant network performance parameters from different sources. Thetransmitter may be configured to forward the combined networkperformance report from the combination unit to a network managementelement and/or an operation and maintenance element, such as e.g. anNM/IRP manager or an O&M device, e.g. for network performance analysisand/or control, thus representing means for forwarding combined networkperformance parameters.

According to embodiments of the present invention, the determinationunit may be configured to determine a triggering event and/or use caseof the received measurement report, thus representing means fordetermining a context of a received measurement report. Thedetermination unit may be configured to accomplish the determination onthe basis of a predefined association between a triggering event and/oruse case and measurements to be performed at the terminal, which may bestored at a local storage. The selection unit may be configured toselect access network-related network performance parameters to beacquired based on the determined triggering event and/or use case, thusrepresenting means for selecting appropriate network information in viewof received terminal information.

For the purpose of transmitting the combined report from said apparatusto a device management and/or operation an maintenance element, there isassumed the existence of a corresponding interface or reference pointbetween e.g. eNodeB or DMS and NM/IRP manager or O&M device, as well asa corresponding manner for such a transmission.

In case of WCDMA, the entity handling a functionality according toembodiments of the present invention, i.e. the apparatus as exemplarilydepicted by FIGS. 7 and 8, may be a radio network controller (RNC) or aNodeB with co-located RNC functionality such as for example in case of aflat architecture solution e.g. of an Internet High speed Packet Access(I-HSPA).

According to certain embodiments of the present invention, the terminalsuch as a user equipment UE or the like is configured to cooperate withthe above-described apparatus, i.e. a DMS or eNode operating accordingto embodiments of the present invention. Accordingly, a terminalaccording to embodiments of the present invention is configured toreceive configuration information concerning measurement logs and/orreporting triggers from said apparatus, to perform correspondingmeasurements for creating corresponding measurement logs, and to reportsuch measurement logs correspondingly via user plane or control plane.

According to certain embodiments of the present invention, the networkmanagement element such as a NM/IRP manager and/or an operation andmaintenance element such as an O&M device is configured to cooperatewith the above-described apparatus, i.e. a DMS or eNode operatingaccording to embodiments of the present invention. Accordingly, anetwork management element and/or operation and maintenance elementaccording to embodiments of the present invention is configured toreceive a combined network performance report from said apparatus, and,possibly, to request corresponding network performance parameters and/orto perform network performance analysis and/or control based thereon.

FIG. 8 shows a block diagram of an apparatus according to exemplaryembodiments of the present invention. In view of the above, the thusdescribed apparatus may be implemented by or at a device managementelement such as e.g. a DMS according to FIGS. 2 and 3, an operation andmaintenance element such as e.g. O&M according to FIGS. 4 and 5, and/oran access network element such as e.g. an eNodeB according to FIGS. 2 to5.

According to FIG. 8, the apparatus according to exemplary embodiments ofthe present invention is configured to perform a method as described inconjunction with FIG. 6. Therefore, while basic operations are describedhereinafter, reference is made to the above description for details.

According to an exemplary embodiment depicted in FIG. 8, the thusdepicted apparatus comprises a receiver, an acquisition unit, a reportcreation unit, a report necessity detection unit, and a transmitter. Itis to be noted that one or more of the acquisition, report creation, andreport necessity detection units may be implemented by a processor. Fora basic implementation, the transmitter may be omitted, as theforwarding of a combined or non-combined report is not necessaryaccording to all embodiments of the present invention.

The receiver may be configured to receive signals from the outside ofthe thus depicted apparatus, e.g. UE measurement reports or informationnecessary for detection of a reporting necessity, thus representingmeans for receiving. The report necessity detection unit may beconfigured to detect a necessity for reporting access network-relatednetwork performance parameters, thus representing means for detecting areporting necessity. The acquisition unit may be configured to(internally or externally) acquire such access network-related networkperformance parameters, thus representing means for acquiring networkperformance parameters. The report creation unit may be configured tocreate an appropriate report on the basis of the available information,i.e. a combined report in case of availability of both terminal-relatedand access network-related network performance parameters, or anon-combined report in case of availability of only accessnetwork-related network performance parameters. Thus, the reportcreation unit represents means fro creating an appropriate networkperformance report. The transmitter may be configured to forward thethus created report when and where appropriate, thus representing meansfor sending a network performance report.

Stated in other words, the apparatus may be configured to send ameasurement report of access network-related parameters without waitingfor a report from the terminal, especially in the case the terminalconnection is lost and the terminal may be expected to access thenetwork again via another apparatus than before, the terminal lackingadditional reporting capability or is otherwise determined to be subjectto malfunction. If the apparatus provides a report without combining itwith the report from the terminal, then it is beneficial to provideadditional information in the report that allows to combine the reportat later phase with possible information received from the terminal. Theinformation to allow such a later combining may e.g. include time stamp,type of the (disconnecting) event experienced, terminal identity, and/orrelated cell and location information, as well as information receivedearlier from the terminal such as handover measurement report data orthe like.

For example, the terminal identity may be particularly beneficial whenthere is (to be) a correlation between terminal-related and accessnetwork-related network performance parameters. Namely, when accessnetwork-related parameters correlate with terminal-related parameters ofone or more specific terminals, the need for reporting accessnetwork-related parameters may be detected in relation with suchspecific terminal(s), and after sending a non-combined report due to thelack of such parameters a later combination may be advantageouslyaccomplished by terminal-related parameters of such specific terminal(s)being identified by the terminal identity or identities used asadditional information in the non-combined report.

In general, it is to be noted that respective functional blocks orelements according to above-described aspects can be implemented by anyknown means, either in hardware and/or software, respectively, if it isonly adapted to perform the described functions of the respective parts.The mentioned method steps can be realized in individual functionalblocks or by individual devices, or one or more of the method steps canbe realized in a single functional block or by a single device.

Generally, any method step is suitable to be implemented as software orby hardware without changing the idea of the present invention. Devicesand means can be implemented as individual devices, but this does notexclude that they are implemented in a distributed fashion throughoutthe system, as long as the functionality of the device is preserved.Such and similar principles are to be considered as known to a skilledperson.

Software in the sense of the present description comprises software codeas such comprising code means or portions or a computer program or acomputer program product for performing the respective functions, aswell as software (or a computer program or a computer program product)embodied on a tangible medium such as a computer-readable storage mediumhaving stored thereon a respective data structure or code means/portionsor embodied in a signal or in a chip, potentially during processingthereof.

Generally, for the purpose of the present invention as described hereinabove, it should be noted that

-   -   method steps and functions likely to be implemented as software        code portions and being run using a processor at one of the        entities, a network element, or a terminal (as examples of        devices, apparatuses and/or modules thereof, or as examples of        entities including apparatuses and/or modules therefor), are        software code independent and can be specified using any known        or future developed programming language, such as e.g. Java,        C++, C, and Assembler, as long as the functionality defined by        the method steps is preserved;    -   generally, any method step is suitable to be implemented as        software or by hardware without changing the idea of the        invention in terms of the functionality implemented;    -   method steps, functions, and/or devices, apparatuses, units or        means likely to be implemented as hardware components at a        terminal or network element, or any module(s) thereof, are        hardware independent and can be implemented using any known or        future developed hardware technology or any hybrids of these,        such as MOS (Metal Oxide Semiconductor), CMOS (Complementary        MOS), BiMOS (Bipolar MOS), BiCMOS (Bipolar CMOS), ECL (Emitter        Coupled Logic), TTL (Transistor-Transistor Logic), etc., using        for example ASIC (Application Specific IC (Integrated Circuit))        components, FPGA (Field-programmable Gate Arrays) components,        CPLD (Complex Programmable Logic Device) components or DSP        (Digital Signal Processor) components; in addition, any method        steps and/or devices, units or means likely to be implemented as        software components may for example be based on any security        architecture capable e.g. of authentication, authorization,        keying and/or traffic protection;    -   devices, apparatuses, units or means can be implemented as        individual devices, apparatuses, units or means, but this does        not exclude that they are implemented in a distributed fashion        throughout the system, as long as the functionality of the        device, apparatus, unit or means is preserved,    -   an apparatus may be represented by a semiconductor chip, a        chipset, or a (hardware) module comprising such chip or chipset;        this, however, does not exclude the possibility that a        functionality of an apparatus or module, instead of being        hardware implemented, be implemented as software in a (software)        module such as a computer program or a computer program product        comprising executable software code portions for execution/being        run on a processor;    -   a device may be regarded as an apparatus or as an assembly of        more than one apparatus, whether functionally in cooperation        with each other or functionally independently of each other but        in a same device housing, for example.

The present invention also covers any conceivable combination of methodsteps and operations described above, and any conceivable combination ofnodes, apparatuses, modules or elements described above, as long as theabove-described concepts of methodology and structural arrangement areapplicable.

In the above, there are disclosed measures for enhancing networkperformance monitoring. Such measures may for example comprise receivinga report on measurements of terminal-related network performanceparameters from a terminal, acquiring information of accessnetwork-related network performance parameters, and combining thereceived terminal-related network performance parameters and theacquired access network-related network performance parameters into acombined network performance report.

Even though the invention is described above with reference to theexamples according to the accompanying drawings, it is to be understoodthat the invention is not restricted thereto. Rather, it is apparent toa skilled person that the present invention can be modified in many wayswithout departing from the scope of the inventive idea as disclosedherein.

The invention claimed is:
 1. A method comprising: in a terminal in aradio access network, receiving measurement configuration informationfrom an access network element in the radio access network; performingmeasurements of terminal-related network performance parameters usingthe measurement configuration information; and transmitting to a networkperformance analysis and/or control element via the access networkelement, the measurements of the terminal-related network performanceparameters via a combined network performance report, wherein thecombined network performance report is formed by attaching accessnetwork-related network performance parameters measured at the accessnetwork element, to the measurements of the terminal-related networkperformance parameters, and the access network-related networkperformance parameters comprise parameters specific for minimization ofdrive tests for network performance monitoring.
 2. The method accordingto claim 1, wherein the access network-related network performanceparameters are acquired by the access network element upon reception ofthe measurements of the terminal-related network performance parametersfrom the terminal.
 3. The method according to claim 1, wherein theaccess network-related network performance parameters are acquired basedon a triggering event and/or use case pertaining to the measurements ofthe terminal-related network performance parameters.
 4. The methodaccording to claim 1, wherein the measurements of the terminal-relatednetwork performance parameters comprise corresponding locationinformation available at the terminal.
 5. The method according to claim1, wherein the network performance analysis and/or control elementcomprises an open mobile alliance device management server.
 6. Themethod according to claim 1, wherein the measurements of theterminal-related network performance parameters are based on parametersspecific for minimization of drive tests and/or self-optimization ofnetworks.
 7. An apparatus in a radio access network, comprising: atleast one processor; and at least one memory including computer programcode, the at least one memory and the computer program code beingconfigured, with the at least one processor, to cause the apparatus toperform the following: receiving measurement configuration informationfrom an access network element in the radio access network; performingmeasurements of terminal-related network performance parameters usingthe measurement configuration information; and transmitting to a networkperformance analysis and/or control element via the access networkelement, the measurements of the terminal-related network performanceparameters via a combined network performance report, wherein thecombined network performance report is formed by attaching accessnetwork-related network performance parameters measured at the accessnetwork element, to the measurements of the terminal-related networkperformance parameters, and the access network-related networkperformance parameters comprise parameters specific for minimization ofdrive tests for network performance monitoring.
 8. The apparatusaccording to claim 7, wherein the access network-related networkperformance parameters are acquired by the access network element uponreception of the measurements of the terminal-related networkperformance parameters from the apparatus.
 9. The apparatus according toclaim 7, wherein the measurements of the terminal-related networkperformance parameters comprise corresponding location informationavailable at the terminal.
 10. The apparatus according to claim 7,wherein the measurements of the terminal-related network performanceparameters are based on parameters specific for minimization of drivetests and/or self-optimization of networks.
 11. A method comprising: inan access network element in a radio access network, receivingmeasurements of terminal-related network performance parameters from aterminal served by the access network element; acquiring information ofaccess network-related network performance parameters, wherein theacquired access network-related network performance parameters aremeasurements performed at the access network element, and the accessnetwork-related network performance parameters comprise parametersspecific for minimization of drive tests for network performancemonitoring; forming a combined network performance report by attachingthe acquired access network-related network performance parameters tothe measurements of terminal-related network performance parameters; andforwarding the combined network performance report to a networkperformance analysis and/or control element.
 12. The method according toclaim 11, comprising determining the access network-related networkperformance parameters upon reception of the measurements ofterminal-related network performance parameters from the terminal. 13.The method according to claim 11, comprising acquiring the accessnetwork-related network performance parameters based on a triggeringevent and/or use case pertaining to the measurements of theterminal-related network performance parameters.
 14. The methodaccording to claim 11, wherein the network performance analysis and/orcontrol element comprises an open mobile alliance device managementserver.
 15. The method according to claim 11, wherein the measurementsof the terminal-related network performance parameters are based onparameters specific for minimization of drive tests and/orself-optimization of networks.
 16. An apparatus in a radio accessnetwork, comprising: at least one processor; and at least one memoryincluding computer program code, the at least one memory and thecomputer program code being configured, with the at least one processor,to cause the apparatus to perform the following: receiving measurementsof terminal-related network performance parameters from a terminalserved by the apparatus; acquiring information of access network-relatednetwork performance parameters, wherein the acquired accessnetwork-related network performance parameters are measurementsperformed at the apparatus, and the access network-related networkperformance parameters comprise parameters specific for minimization ofdrive tests for network performance monitoring; forming a combinednetwork performance report by attaching the acquired accessnetwork-related network performance parameters to the measurements ofterminal-related network performance parameters; and forwarding thecombined network performance report to a network performance analysisand/or control element.
 17. The apparatus according to claim 16,comprising: at least one processor; and at least one memory includingcomputer program code, the at least one memory and the computer programcode being configured, with the at least one processor, to cause theapparatus to perform the following: determining the accessnetwork-related network performance parameters upon reception of themeasurements of terminal-related network performance parameters from theterminal.
 18. The apparatus according to claim 16, comprising: at leastone processor; and at least one memory including computer program code,the at least one memory and the computer program code being configured,with the at least one processor, to cause the apparatus to perform thefollowing: acquiring the access network-related network performanceparameters based on a triggering event and/or use case pertaining to themeasurements of the terminal-related network performance parameters. 19.The apparatus according to claim 16, wherein the network performanceanalysis and/or control element comprises an open mobile alliance devicemanagement server.
 20. The apparatus according to claim 16, wherein themeasurements of the terminal-related network performance parameterscomprise parameters specific for minimization of drive tests and/orself-optimization of networks.